Overview

Analagous to our handling of non-.json custom labware upload, we want to disallow upload of .py or .json files on Desktop. Expected behavior is to check the filename extension of the prospective uploaded file (erring on the side of lenient acceptance), and close the slideout and make error toast if the extension is not .py or .json.

Closes RQA-2959

Test Plan and Hands on Testing

• On Desktop, navigate to Protocols landing and select 'Import'
• On slideout, import a non-.json or .py file through file explorer or drag-and-drop
• Verify that slideout closes and "Incompatible file type" error toast renders
• Repeat with a .json or .py file and verify that slideout closes and protocol is added and analysis begins

With other protocols:

With no other protocols:

Changelog

• Check attempted uploaded protocol file extension before adding protocol
• Make toast and close slideout if invalid file

Review requests

• See code and test plan. If there is a different pattern for file type checking as specified in isValidProtocolFileName, I can update.

Risk assessment

Low-medium. We want to allow any attempted upload within reasonable file type matching